home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Patches 1995 March
/
SGI IRIX Patches 1995 Mar.iso
/
relnotes
/
patchSG0000315
/
ch1.z
/
ch1
Wrap
Text File
|
1995-03-10
|
11KB
|
265 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_0_3_1_5__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0000315 to IRIX 5.3
1.1 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for all platforms.
1.2 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for Fortran 4.0.1 Release.
The software cannot be installed on other configurations.
1.3 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_0_3_1_5
This patch contains fixes for the following bugs in IRIX
5.3. Bug numbers from Silicon Graphics bug tracking system
are included for reference.
+o AAAAssssssssiiiiggggnnnniiiinnnngggg oooorrrr iiiinnnniiiittttiiiiaaaalllliiiizzzziiiinnnngggg aaaa cccchhhhaaaarrrraaaacccctttteeeerrrr vvvvaaaarrrriiiiaaaabbbblllleeee wwwwiiiitttthhhh aaaa
bbbbiiiitttt ccccoooonnnnssssttttaaaannnntttt ((((BBBBuuuugggg IIIIDDDD 222255555555999955555555))))
The compiler has been extended to allow the use of a
bit constant in assiging ot initializing a character
variable which has a size corresponding to a numeric
variable. In other words, a character variable of size
1, 2, 4, 8, or 16 can now be initialized or assigned a
numeric bit constant value.
+o GGGGeeeennnneeeerrrraaaattttiiiinnnngggg FFFFoooorrrrttttrrrraaaannnn eeeexxxxtttteeeerrrrnnnnaaaallll ssssyyyymmmmbbbboooollllssss wwwwiiiitttthhhhoooouuuutttt tttthhhheeee
aaaappppppppeeeennnnddddeeeedddd uuuunnnnddddeeeerrrrssssccccoooorrrreeee ((((BBBBuuuugggg IIIIDDDD 222255555555999966660000))))
A compilation option -_W_f,-_n_o_a_p_p_e_n_d is added to suppress
the automatic generation of an appended unerscore to
all Fortran external symbols. Note that this option
must be used with special care as many non-intrinsic
supporting routines in the Fortran runtime libraries
are defined with the appended underscore and won't be
used to resolve those symbols without the appended
underscore. For example, a call to _f_s_e_e_k(_3_F) with this
option will be resolved by the C version of fseek().
In order to use the Fortran version of fseek(3F) when
this compilation option is used, the user must
explicitly specify the appended underscore and make
call to call fseek_().
+o SSSSPPPPeeeecccciiiiffffyyyyiiiinnnngggg bbbbiiiitttt ccccoooonnnnssssttttaaaannnnttttssss wwwwiiiitttthhhhoooouuuutttt ssssuuuurrrrrrrroooouuuunnnnddddiiiinnnngggg qqqquuuuooootttteeeessss iiiinnnn
aaaa DDDDAAAATTTTAAAA ssssttttaaaatttteeeemmmmeeeennnntttt ((((BBBBuuuugggg IIIIDDDD 222255558888999955558888))))
The compiler is extended to allow the use of bit
constants starting with character 'z', 'x', 'o', or 'b'
- 2 -
and followed by the appropriate hexadecimal, octal, or
binary digits to be used in a DATA statement where
constants are expected without the need to be enclosed
by quotes. For example, _z_f_0_f_0 is recognized as a
hexadecimal number 'f0f0' in a DATA statement where the
syntax requires a constant. In all other contexts,
zf0f0 is still treated as a normal variable.
+o LLLLooooggggiiiiccccaaaallll OOOO@@@@////AAAANNNNDDDD eeeexxxxpppprrrreeeessssssssiiiioooonnnnssss ggggaaaavvvveeee iiiinnnntttteeeennnnaaaallll _uuuu_gggg_eeee_nnnn eeeerrrrrrrroooorrrr ((((BBBBuuuugggg
IIIIDDDD 222255557777222233335555))))
When a logical AND/OR expression is of type LOGICAL*1
or LOGICAL*2, incorrect VREG _u_c_o_d_e could be generated
causing _u_g_e_n to give an internal error "offset/length
mismatch between vreg and reference".
+o VVVVaaaarrrriiiiaaaabbbblllleeeessss iiiinnnnddddiiiirrrreeeeccccttttllllyyyy eeeeqqqquuuuiiiivvvvaaaalllleeeennnncccceeeedddd ttttoooo aaaa ccccoooommmmmmmmoooonnnn bbbblllloooocccckkkk
vvvvaaaarrrriiiiaaaabbbblllleeeessss ((((BBBBuuuugggg IIIIDDDD 222266662222333333335555))))
Fixed a bug where multiple variables indirectly
equivalenced to a variable in a common block could
cause incorrect storage assignment to be generated.
The bug could cause an invalid compilation error
message regarding "inconsistent common usage" or
incorrect runtime result.
+o PPPPrrrrooooggggrrrraaaammmm ccccoooorrrreeeedddduuuummmmppppssss oooorrrr ggggiiiivvvveeeessss iiiinnnnccccoooorrrrrrrreeeecccctttt rrrreeeessssuuuulllltttt tttthhhheeee
iiiinnnnttttrrrriiiinnnnssssiiiicccc ffffuuuunnnnccccttttiiiioooonnnn _iiii_nnnn_dddd_eeee_xxxx_((((_3333_ffff_)))) iiiissss uuuusssseeeedddd aaaassss aaaannnn aaaaccccttttuuuuaaaallll
aaaarrrrgggguuuummmmeeeennnntttt iiiinnnn aaaa ffffuuuunnnnccccttttiiiioooonnnn ccccaaaallllllll ((((BBBBuuuugggg IIIIDDDD 222255552222666600008888))))
The intrinsic function _i_n_d_e_x(_3_f) was misinterpreted as
returning integer*2 result and so could give an
incorrect result, especially when used as an actual
argument in a function call. A problem when the
intrinsic function _i_n_d_e_x(_3_f) did not work when compiled
with the -_i_8 option was also fixed.
Note that this patch requires patch313 to provide the
runtime library support for 64bit _i_n_d_e_x(_3_f). If you
use _i_n_d_e_x(_3_f) and compile your program with -_i_8 option
without having _p_a_t_c_h_3_1_3 you will get a linker message
that _l__i_n_d_x is unresolved. You should request the TAC
for patch313 then.
1.4 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_0_3_1_5
This patch release includes these subsystems:
+o patchSG0000315.ftn_dev_sw.ftn
- 3 -
1.5 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install patches for only the problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed in
this patch, determine the patches that meet your specific
needs.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _I_R_I_S
_S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e to bring up the miniroot form of
the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst>prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Select the desired patches for installation.
3. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
4. You may find that two patches have been marked as
incompatible. If this occurs, you must deselect one
of the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
5. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
- 4 -
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.